docs: §5.4 dig-rpc-beside exemption (mTLS keyless-peer RPC exempt from payload-seal) - #43
Closed
MichaelTaylor3d wants to merge 1 commit into
Closed
docs: §5.4 dig-rpc-beside exemption (mTLS keyless-peer RPC exempt from payload-seal)#43MichaelTaylor3d wants to merge 1 commit into
MichaelTaylor3d wants to merge 1 commit into
Conversation
…ers exempt from payload-seal) Document that directed node↔node RPC over mTLS between keyless peers is exempt from the ecosystem-wide end-to-end payload-seal rule, as mTLS itself provides the necessary e2e authentication and confidentiality. Payload-seal applies to directed messages with DID-keyed recipients (chat/email/video/IPC), not autonomous peers. Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Author
|
Closing — the §5.4 dig-rpc-beside EXEMPTION this documented is WITHDRAWN. @MT-Dev reversed the decision (2026-07-19): node↔node RPC payloads MUST be sealed to the recipient node's key (recipient-binding, not mTLS-only). New docs will follow the #1075 node-seal design. Do not merge this exemption. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document the §5.4 ecosystem-wide exception: directed node↔node RPC over mTLS between keyless peers (identified by transport
peer_id, not DID) is exempt from the end-to-end payload-seal rule, because mTLS itself provides the necessary end-to-end authentication and confidentiality. The payload-seal rule applies to directed messages with DID-keyed recipients (dig-chat, dig-email, dig-video-chat, and any future channel where the recipient is a user's DID-anchored identity).This clarifies the scope of the ecosystem-wide §5.4 hardening rule: autonomous network peers over mTLS are exempt; user-to-user directed channels are not.
Changes
docs/protocol/peer-network.mdclarifying the exemption and its boundaries.🤖 Generated with Claude Code